Improve formulation builder disabled-state accessibility#1223
Conversation
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
Warning Review limit reached
Next review available in: 15 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
CI triageCI failed on this PR. Automated classification of the 2 failed job(s):
Compared with main CI run #5589 (success). Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger. |
Summary
disabledsemantics while keeping labels readable in light, dark, and forced-colors modesRAG impact: no retrieval behaviour change — UI-only disabled-state styling; no retrieval, ranking, answer, or source behavior changed.
Verification
npm run verify:pr-local— passed on the clean current-main branch; includes build, client-bundle secret scan, 3,421 unit tests, and offline RAG fixture validationnpm run verify:ui— equivalent product/test content passed all seven formulation journeys in PR Improve formulation builder disabled-state accessibility #1219; the prior local full run was 272/273 with only system Chrome’s unrelated PWAin-incognitoresult. This replacement requires clean hosted Production UI before merge.npm run verify:release— not run; provider-backed and not required for this UI-only changenpm run verify:cheap: 3,421/3,421 passedRisk and rollout
70dd8cd9; no database or migration rollback is involved.Clinical Governance Preflight
N/A — UI-only disabled-state presentation; no ingestion, answer generation, retrieval/ranking, source rendering, document access, privacy, production environment, or clinical output behavior changed.
Notes
main, created because PR Improve formulation builder disabled-state accessibility #1219 became GitHub-conflicted after automated branch synchronization. PR Improve formulation builder disabled-state accessibility #1219 must not merge.agent/formulation-disabled-contrastworktree remains preserved but unavailable. This PR does not modify or discard it.